Methods and systems for improved system performance

ABSTRACT

Methods and systems are provided for improving system responsiveness while increasing efficiency and scalability of network communication by combining reliable and unreliable network transports. A method and system is provided for client polling a status server to see if there is new data, receiving a notification that there is new data, sending a client request to a server premises which retrieves the new data from a database and returns the new data to the client. Communication with the status server uses an unreliable packet or a reliable packet, whereas communication between the client and the server premises uses reliable transport. A redundant cluster of status servers and methods is provided.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patent application Ser. No. 12/019,568, filed Jan. 4, 2008, which is a non-provisional of and claims the benefit of U.S. provisional Application No. 60/886,439, filed Jan. 24, 2007.

BACKGROUND

The field of home and small business security is dominated by technology suppliers who build comprehensive ‘closed’ security systems, where the individual components (sensors, security panels, keypads) operate solely within the confines of a single vendor solution. For example, a wireless motion sensor from vendor A cannot be used with a security panel from vendor B. Each vendor typically has developed sophisticated proprietary wireless technologies to enable the installation and management of wireless sensors, with little or no ability for the wireless devices to operate separate from the vendor's homogeneous system. Furthermore, these traditional systems are extremely limited in their ability to interface either to a local or wide area standards-based network (such as an IP network); most installed systems support only a low-bandwidth, intermittent connection utilizing phone lines or cellular (RF) backup systems. Wireless security technology from providers such as GE Security, Honeywell, and DSC/Tyco are well known in the art, and are examples of this proprietary approach to security systems for home and business. There remains, therefore, a need for systems, devices, and methods that easily interface to and control the existing proprietary security technologies utilizing a variety of wireless technologies.

SUMMARY

A computing device may be in communication with one or more remote devices. The computing device may send a request to one of the remote devices to determine if new data associated with the computing device is available. The computing device may send the request via an unreliable protocol. The computing device may receive response to the request, such as via the unreliable protocol. The response may indicate that new data associated with the computing device is available.

The computing device may send a request to another remote device for the available data. The computing device may send the request via a reliable protocol. In response, the computing device may receive the available data, such as via the reliable protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of a client server system according to an embodiment.

FIG. 2 depicts a block diagram of a server premises according to an embodiment.

FIG. 3 depicts a block diagram of a client-server system using reliable and unreliable transports according to an embodiment.

DETAILED DESCRIPTION

A client-server architecture consists of a client making requests to a server. The server cannot contact the client directly, so the client polls the server periodically to see if there is any new data for it. A reliable transport is used in order to assure reliable synchronization between the server and client. On an IP network, that means using TCP as the transport, often with HTTP/XML/SOAP riding on top of it.

According to various embodiments, combination of technologies are used to improve the responsiveness of such a client-server system while at the same time reducing load on the client, the server and the network according to various embodiments.

FIG. 1 illustrates a client-server system. At the client premises, a client program, either on a PC or an Internet appliance/gateway, needs to stay in sync with data on a server at a remote location. FIG. 1 shows the database on the server where current information for that client is stored. In most cases, it is impossible—or at least highly unreliable and subject to security risks—for the client program to listen for update data coming from the server. Home users typically use a broadband router that acts as a firewall and prevents incoming data requests. Hence the practical solution is for the client to poll the server periodically see if there is any new data that the client needs to retrieve.

FIG. 2 illustrates a server installation. Requests first come in through firewall hardware (1). Next they are passed to a web server (2) which checks where to dispatch the request. As this is dynamic data, the web server will pass it on to an application server (3) to retrieve the data. The data is stored in a database, so the application server ultimately needs to query the database server (4) to get the current status.

This process winds up taking up many processor cycles and related resources at the server premises:

-   -   TCP connections require additional statefull management by the         firewall     -   Web server needs to handle the request, write logs, pass on the         request to the application servers     -   Application server decodes the request and sends a data access         request to the database server     -   Database server accesses the data and returns it

In addition, the networks that connect these servers would have to typically carry the additional traffic connected with the request.

If the client is a modern PC, then it would typically be able to handle the load of frequent synchronization requests to a single server. However, if the client is a lower-powered Internet appliance, formatting and managing a TCP connection and a request-response session can be costly in terms of processor cycles and memory. Even if there were zero cost on the server or network side, such a client cannot afford the overhead of frequent polling of its server via its web service. Frequent server polls may well have a deleterious effect on overall appliance performance, possibly more than negating any improvements achieved due to rapid polls.

In order to appear responsive to changes, the client may need to make “frequent” requests of the server, at some predetermined poll rate. Frequent requests may put an extra load on both the server and the client, as well as the network transport.

One approach is to use a variable poll rate, possibly improving responsiveness in cases where the likelihood of new data is known beforehand. But this does not help at all if the data updates from the server are infrequent and not predictable.

Ideally there would be a way to provide rapid response without the costly overhead to the client, server or network.

The standard, reliable client-server interaction may be combined with a separate, out-of-band unreliable transport “connection”. As shown in FIG. 3, a third-party server serves as a “status” server. It provides unreliable access to the current status of data for the client (“do I need to sync?”). Because it is unreliable (using only a UDP Datagram packet under TCP/IP), it does not incur the overhead of TCP connections. Even a small client appliance can make frequent UDP requests to the status server without impacting its ordinary work. Since its normal poll rate can be greatly reduced or eliminated, the client does not incur server-sync TCP overhead nearly as often as it does without the status server.

When the server does have new data for the client, it notifies the status server, which updates its cache. The next time the client checks with the status server, the client will see that there is new data for the client and the client contacts its server via its TCP web service in the usual way.

-   -   1. Certain embodiments of the system may include the following,         or various subsets or combinations thereof:     -   2. A client-server architecture where the client can make         requests of the server but not vice versa.     -   3. The client-server architecture uses a reliable transport for         synchronization messages     -   4. The server occasionally has new data to send down to the         client     -   5. A third-part server is added that         -   1. Is not vital to the operation of the system—the system             runs, albeit at a reduced responsiveness, without it (it             does not replace any of the existing client-server             synchronization functionality)         -   2. It is a single server, or small cluster of servers             -   1. Since it is not vital, it is “allowed” to fail                 temporarily             -   2. That means it can operate from its own cache in RAM,                 making it very fast and scalable                 -   1. Only a tiny amount of information needs to be                     kept for every client, so any modern server will                     have more than enough RAM to accommodate an entire                     data center's worth of clients                 -   2. It does not use a database—no DB overhead                 -   3. It does not need to communicate with any other                     servers—no additional local network traffic                 -   4. It does not do any logging—saving considerable                     processor cycles and disk usage.         -   3. It uses unreliable UDP Datagram packet exchange for its             communication

The result is that, at a very low cost in 1) server usage, 2) client processor cycles, and 3) data center bandwidth, the responsiveness of the overall system can be greatly improved.

According to an embodiment, redundant status servers may be used. In an embodiment, the single status server is replaced by a cluster of servers that share the same status data. This will incur at least the cost of additional communication between servers, possibly through a database. Nevertheless, various of the client and bandwidth utilization benefits described above may be achieved in some embodiments with such an alternate redundant-server configuration.

In an embodiment, a reliable transport (i.e. TCP/IP) is used for the status checks. This may incur at least the cost of additional communication between servers, and additionally does not reduce the traffic or load on the client side. However, this does still provide a way to reduce the load on the server farm while still providing the low-latency advantages.

For example, an embodiment comprises any of the above systems or methods alone or in combination as part of a network for premises management. The network may include premises management devices such as a smart thermostat. The premises management devices are connected to a premises network which can be, for example, an RF and/or power line network. The premises network is connected to a gateway which in turn is connected to a broadband device such as a DSL, cable, or T1 line. The gateway can alternatively or also be connected to a dial up modem. The premises is connected to the Internet according to an embodiment. The Internet is connected to system managers at the network operations center. The Internet is also connected to customers of the system manager, for example vendors such as premises vendors, communication service vendors, or Internet portal vendors. The Internet is also connected to vendees, such as premises vendees, communication service vendees, or Internet portal vendees.

An embodiment may include programmable code and devices with screens of a portal interface for premises management. For example, code with may summarize premises management services. Code may summarize security management services and safety management services. Code may also summarize energy management services. Services offered by the system can be branded and incorporated into a third part web portal, for example, in a personal portal such as one provided by Yahoo.

The look and feel of the system pane can be tailored by the service provider.

In an embodiment, a system portal summary page may show a snap-shot of the state of the various devices in the user premises. For example, in an embodiment, the user can change premises by clicking on this box and selecting a different premises. A status pane may list the different devices in the user premises along with their actual states. A pending updates pane may show the time of the last communication between the premises and the server as well as any pending updates waiting to be sent downlink to the premises. The pictures pane shows the last several (e.g. last four) pictures taken by the camera in the user premises. The user can click on a thumbnail picture to look at a larger version of the photo as well as access archived images for that camera, look at live video, take new pictures or delete photos. The schedule pane shows the schedules activities for the premises. The alarm history shows an archive of the most recent event and activity in the user premises. The reminders pane provides a means for the system to remind the user to perform certain activities or functions related to their home or business. The mode drop down button on the blue navigation bar allows the user to switch between the systems modes. The QuikControl drop down allows the user to control any device that is controllable (e.g. camera, thermostat, lamps, etc.).

According to an embodiment, a method is provided for premises management networking. Premises management devices connected to a gateway at a premises are monitored and controlled. According to an embodiment, n uplink-initiation signal associated with a network operations center server is received at the premises. In response to the uplink-initiation signal, communications between the gateway and the network operations center server may be initiated from the gateway at the premises. During the communications between the gateway and the network operations center server, information associated with the premises management devices may be communicated.

The premises gateway can be a low-cost and stand-alone unit that connects the in-premises devices to the server. The connectivity to the Internet can be accomplished via a broadband connection (T1, DSL or cable) and/or via the telephone line. Though broadband connectivity may be used, telephone connectivity may be present as a back-up option in case the broadband connection is lost. For premises without a broadband connection (e.g., vacation homes) a telephone-only connection can be used.

A user account may be established by the end user using personal information (name, payment option, etc.) of the user. The account registration may involve the user logging on to the system manager web site and establishing a new account by entering name, address, phone number, payment details and/or the gateway serial number printed on the gateway in the end user's possession. In some cases the system manager service account may already be pre-established with the gateway serial number and the end user simply has to update the account with personal and payment information. Multiple gateways can also be handled per user account.

The gateway may be registered to associate the user account on the system manager server (established in the previous step) with an actual gateway in the user's home. The gateway is connected to a broadband network or the telephone line in the home.

An embodiment may help provide users with a hosted and managed service for premises device monitoring and control for a fee, such as a monthly subscription fee. The premises markets include residential homes, commercial MTUs as well as small businesses.

Embodiments may provide device logging, activity logging and tracking. For example, an embodiment can log any device variable specified by the user for up to, for example, 30 days. The user defines a logging interval for each variable at the time of configuration. The logging feature can be handled by the gateway on the local device side and the data can be transferred to the server at regular intervals. The overall variable log for all variables can be kept on the server side. Logging of data for more than, for example, 30 days (but no more than, for example, 180 days) can be provided to the user, for example for a nominal fee. An embodiment may provide at least, for example, a 14-day history log of all user, system and device actions. An action includes a change to a device variable, system or network settings brought on by either the system or the user (e.g., variable changed, logging enabled, device added, user notified, etc.). The user can trace back system activities to their cause and to the date and time they occurred. Past activities can be searched by variable, device, category or date.

An embodiment can support user-defined modes, such as “home,” “away,” “sleep,” “vacation,” etc. The mode the user network is in plays a factor in the determination of the actions taken (reporting, alarming, eventing, notification, etc.) by the system when variable changes occur. According to an embodiment, the user can specify alarm conditions for variables with discrete states (e.g., binary ON/OFF). These alarms can be reported in real-time (i.e., immediate uplink) by the gateway to the server. The server then in turn looks at the data and determines, based on user alarm settings, whether to notify the user or not.

According to an embodiment, for non-critical events, the system can notify the user in non-real-time fashion regarding the state of any variable specified by the user. The variables chosen for user eventing can be of any kind (discrete or continuous). The gateway updates the server with the change of variable state/value at a regularly scheduled upload. The server continuously looks at variable data and determines, based on user eventing settings, whether to notify the user or not. Eventing conditions can be determined based on the value or state of a variable as well as the system mode. According to an embodiment, the system can support user alarming and eventing via the following methods: email, text messaging, pager, and/or voice telephone call (voice synthesis).

An embodiment may provide device data monitoring and control. The user can specify any device variable for monitoring and control via the server portal. For example, up to 255 devices can be supported by a single gateway. For example, up to 512 variables can be supported by a single gateway.

The system can support an open architecture where most, if not all device networking protocols can be supported. Examples of specific device protocols supported by the system include RF and powerline protocols, such as GE Interlogix RF and Echelon LonWorks power line (PL & FT), simplifying the installation burden by requiring no new wires to be installed in a premises. The LonWorks free topology twisted pair medium (FT-10) can be supported as an option to support certain commercial applications (e.g., office buildings).

The following is a non-exhaustive list of a few other devices that may be supported by the system according to various embodiments.

Small data/message display—for text messages, news, weather, stock, photos, etc.

-   -   1. Door latch control     -   2. Pool/spa controller     -   3. Weather station     -   4. Lighting control     -   5. Elderly or disabled monitoring     -   6. Irrigation controller (Bibija)     -   7. VCR programming

The system can support cameras. For example, standard off-the-shelf IP cameras (also referred to as web cameras) may be used, such as those available from vendors such as Axis, Panasonic, Veo, D-Link, and Linksys, or other cameras manufactured for remote surveillance and monitoring. Surveillance cameras may contain a standalone web server and a unique IP address may be assigned to the camera. The user of such a camera would typically retrieve the camera image by accessing the camera's web page through a standard web browser, using the camera's IP address. In some cases the IP camera acquires a local IP address by using a DHCP client to negotiate an address from the local DHCP server (usually residing in the user's router/firewall).

According to an embodiment, a gateway can initiate all communications with the server. Gateway communication can either initiate based on a predetermined schedule (e.g., every 30 minutes) or due to a local premises alarm (selected by the user).

Gateways can contact a common server for their first uplink connection in order to obtain their assigned gateway server address, which they can use for all subsequent uplink connections (unless changed later by the system). In the event that the gateway cannot connect to its designated gateway server, it can fall back to contacting the default initial gateway in order to refresh its gateway server address.

The predetermined call initiation schedule can be programmable by the server and can provide different intervals for broadband and telephone intervals (e.g., every 30 minutes for broadband and every 90 minutes for telephone).

An embodiment may be directed to a control network having a collection of sensor and actuator devices that are networked together. Sensor devices sense something about their surroundings and report what they sense on the network. Examples of sensor devices are door/window sensors, motion detectors, smoke detectors and remote controls.

Actuator devices receive commands over the network and then perform some physical action. Actuator devices may include light dimmers, appliance controllers, burglar alarm sirens and cameras. Some actuator devices also act as sensors, in that after they respond to a command, the result of that command is sent back over the network. For example, a light dimmer may return the value that it was set to. A camera returns an image after has been commanded to snap a picture.

In addition to the foregoing, the following are various examples of embodiments.

Some embodiments of a method for premises management networking include monitoring premises management devices connected to a gateway at a premises; controlling premises management devices connected to the gateway at the premises; receiving, at the premises, an uplink-initiation signal associated with a network operations center server; and in response to the uplink-initiation signal, initiating, from the gateway at the premises, communications between the gateway and the network operations center server; and communicating, during the communications between the gateway and the network operations center server, information associated with the premises management devices.

The uplink-initiation signal can be received via telephone and/or broadband connection. The gateway can initiate communications between the gateway and the network operations center server with at least an HTTP message and/or at least an XML message. The premises management devices can manage energy of the premises, security of the premises, and/or safety of the premises. Many embodiments provide a hosted solution for property developers, owners and managers as well as service providers (ISPs, telcos, utilities, etc.) such as communication service providers and internet portal providers. Some embodiments offer a complete, turnkey, reliable, and/or cost-effective solution for the delivery of telemetry services (e.g., energy management, security, safety, access, health monitoring, messaging, etc.) to customers.

An embodiment is directed to a business method for premises management. Some embodiments of a business method for premises management include making an Internet portal available for access to a vendee, such as a premises vendee, communication service vendee, and/or an Internet portal vendee; and at least after a transaction between the vendor and the vendee, such as a premises transaction, a communication services transaction, and/or Internet portal services transaction, providing premises management services via the Internet portal to the vendee.

The Internet portal can be branded with a brand of the vendor according to an embodiment. Examples of a premises vendor include a home builder, premises builder, and premises manager. Examples of a premises vendee include a home buyer, premises buyer, and premises tenant. Examples of a communication service vendor include an Internet service provider, a telephone company, a satellite television company, and a cable television company. Examples of a communication service vendee include a customer of the Internet service provider, a customer of the telephone company, a customer of the satellite television company, and a customer of the cable television company. Premises management services can manage energy of the premises, security of the premises, and/or safety of the premises.

An embodiment is directed to a system. The system includes a network of premises management devices, a gateway coupled to the network and premises management devices, a server coupled to the gateway by a communication medium and a portal coupled to the communications medium. The portal provides communication with the premises management devices.

According to various embodiments alone or in various combinations: the communications medium may comprise the Internet; the portal may comprise an internet portal; and/or the portal may be branded with the name of a vendor of a product associated with the premises. The product may comprise a building, and/or the vendor may comprise a party that leases the premises. The vendor may also or alternatively comprise a property management organization. The server may be included within a network operations center. The logic may comprise, according to various embodiments, software, hardware, or a combination of software and hardware.

Another embodiment is directed to a gateway. The gateway includes an interface coupled to a network of premises management devices, logic that receives data from different premises management devices, and an interface coupled to a communications medium that is coupled to a server. The server is coupled to a portal coupled to the communications medium. The portal provides communications with the premises management devices.

According to various embodiments alone or in various combinations: the communications medium may comprise the Internet; the portal may comprise an internet to portal; and/or the portal may be branded with the name of a vendor of a product associated with the premises. The product may comprise a building; the vendor may comprise a party that leases the premises; the vendor may comprise a property management organization; and/or the server may be included within a network operations center.

Provided herein is a method for network communication comprising a client polling a server to see if there is new data for the client to receive. If there is new data for the client to receive, the client may receive a first notification from the server that there is new data for the client to receive. The polling may use uses a packet. The polling may use an unreliable packet. The polling may use an unreliable datagram packet. The polling may use a reliable packet. The polling may use a transmission control protocol packet (TCP) as a reliable packet. If there is new data for the client to receive, the status server may send a notification to the client, and the client, upon receiving the notification, may send a client request for the new data to a server premises. The sending and receiving of the first notification may use, for example, at least one of a reliable packet, an unreliable packet, an unreliable datagram packet (UDP) and a transmission control protocol packet (TCP) as a reliable packet. The sending and receiving of the first notification may use a packet. The packet may be referred to as the first packet herein. The server premises may comprise a system server and a database. Upon receiving the client request, the system server retrieves the new data from the database. The client receives the new data from the server premises. In some embodiments, the client sends the client request to the server premises and the client receives the new data from the server premises using reliable transport. In some embodiments, the reliable transport is TCP. In some embodiments, the reliable transport comprises a transmission control protocol packet (TCP). Reliable transport may be with at least one of XML, HTTP, and SOAP riding on top of it.

The server premises may comprise a system server and a database. The system server may comprise a firewall, a web server, an application server, and a database server.

In some embodiments, the step of the system server retrieving the new data comprises the application server decoding the client request and sending a data access request to the database server. In some embodiments, the step of the system server retrieving the new data further comprises the database server accessing the new data from the database and returning the new data to the application server.

The client may comprise a low powered Internet-appliance. The client may comprise a gateway.

The method may further comprise the system server notifying the server that there is new data. Upon notification that there is new data, the server may update its cache to indicate there is new data for the client. While they are not necessarily interchangeable (although in some embodiments, they may be), attributes (or lack thereof) of the server may exist (or fail to exist) in the status server. Likewise, attributes (or the lack thereof) of the status server may exist (or fail to exist) in the server, The server may be also referred to as the first server herein.

In some embodiments, the method further uses a redundant system having a second server that is pollable to determine whether there is new data for the client. The method comprises the client polling the second server to see if there is new data for the client to receive, the client receiving a second notification from the second server that there is new data for the client to receive, and upon receiving the second notification, the client sending a client request for the new data to the server premises. The client polling of the second server may use a second packet. The second packet may be unreliable. The second packet may be an unreliable datagram packet (UDP). The second packet may be reliable. The second packet may be a transmission control protocol packet (TCP). The second server may have all the attributes (or lack thereof) of a status server. The second server may have all the attributes (or lack thereof) of a server as described or referenced herein. The second server may be a status server. The sending of the client request to the server premises uses reliable transport. In some embodiments, the reliable transport is TCP. In some embodiments, the reliable transport comprises a transmission control protocol packet (TCP). Reliable transport may be with at least one of XML, HTTP, and SOAP riding on top of it.

The first server and the second server may make up a cluster of servers. Additional redundant servers may be added similarly for polling and determining if there is new data for the client. Any one (or more than one, or all) of the messages between the server and the client, or between the server and the server premises may fail. The method may comprise one of the first server and the second server failing to notify the client that there is new data for the client to receive. The server may be polled more frequently to adjust for this. Additional redundant servers may be added to the cluster and used similarly to the first server and/or the second server to ensure the message that there is new data for the client to receive is not lost for long.

Provided herein is a network communication system comprising a server premises comprising a system server and a database and a client. The client may comprise logic that polls a first server to see if there is new data for the client to receive, logic that receives a first notification from the server that there is new data for the client to receive, logic that, when the client receives the first notification, sends a client request to the server premises to retrieve the new data, and logic that receives the new data from the server premises. The system server may comprise logic that upon receiving the client request, retrieves the new data from the database. The logic that polls the first server and the logic that receives the first notification may use a packet. The packet may be an unreliable packet. The packet may be an unreliable datagram packet. The packet may be a reliable packet. The packet may be a transmission control protocol packet (TCP). The logic that sends the client request to the server premises and the logic that receives the new data from the server premises use reliable transport. In some embodiments, the reliable transport is TCP. In some embodiments, the reliable transport comprises a transmission control protocol packet (TCP). In some embodiments, the reliable transport is with at least one of XML, HTTP, and SOAP riding on top of it.

The client may comprise a low powered Internet appliance. The client may comprise a gateway.

In some embodiments, the system server comprises a firewall, a web server, an application server, and a database server. In some embodiments, the application server comprises logic that decodes the client request and sends a data access request to the database server. The database server may comprise logic that accesses the new data from the database and returns the new data to the application server. The system server may comprise logic that notifies the first server that there is new data. The system server may comprise logic that notifies the second server that there is new data.

The server may comprise logic that updates its cache to indicate there is new data for the client. The server may comprise a tiny amount of information for a client. The server may comprise only a tiny amount of information for a client. The server may be configured to not use a database in its communications with the client and with the server premises. The server may be configured to not need to communicate with servers other than the system server (although it may or may not have such capability). In some embodiments, the server may be configured to not do logging (although it may or may not have such capability). In some embodiments, the server is a status server. While they are not necessarily interchangeable, attributes (or lack thereof) of the server may exist (or fail to exist) in the status server. Likewise, attributes of the status server (or the lack thereof) may exist (or fail to exist) in the server, The server may be also referred to as the first server herein.

In some embodiments, the system uses a redundant system including a second server. The client may further comprise logic that polls the second server to see if there is new data for the client to receive, logic that receives a second notification from the second server that there is new data for the client to receive, and logic that, when the client receives the second notification, sends the client request to the server premises to retrieve the new data. In some embodiments, the logic that polls the second server and the logic that receives the first notification may use a packet. The packet may be an unreliable packet. The packet may be an unreliable datagram packet. The packet may be a reliable packet. The packet may be a transmission control protocol packet (TCP). The second server may have all the attributes (including the lack thereof) of a status server. The second server may have all the attributes of a server as described or referenced herein. The second server may be a status server.

In some embodiments, at least the first server and the second server make up a cluster of servers. Additional servers may be added similarly for polling and determining if there is new data for the client. As a result, any one (or more than one, or all) of the messages between the server and the client, or between the server and the server premises may fail. In some embodiments, one of the first server and the second server may fail to notify the client that there is new data for the client to receive. The server may be polled more frequently to adjust for this. Additional servers may be added to the cluster and used similarly to the first server to ensure the message that there is new data for the client to receive is not lost for long. The first, second, third, fourth, or any of the servers in the cluster of servers may have the features of the server mentioned herein. Likewise, the attributes made in reference to any specific server (i.e. the first server, the second server, etc.) can be additionally or alternatively attributed to any of the servers in the cluster of status servers. Any number of the servers in the cluster of servers may be status servers, or none at all.

In some embodiments of the system, the logic comprises hardware. In some embodiments of the system, the logic comprises software.

Provided herein is a network communication system comprising a server premises comprising a system server and a database, the system server comprising logic that upon receiving a client request, retrieves new data from the database, a server comprising logic that upon polling a packet, sends a notification using a packet, and a client comprising logic that polls the server using a packet to see if there is new data for the client to receive, logic that receives the notification from the server using a packet that there is new data for the client to receive, logic that, when the client receives the notification, sends a client request to the server premises using reliable transport to retrieve the new data, and logic that receives the new data from the server premises using reliable transport.

In some embodiments, the server is a status server. While they are not necessarily interchangeable (although in some embodiments they may be), attributes (or lack thereof) of the server may exist (or fail to exist) in the status server. Likewise, attributes of the status server (or the lack thereof) may exist (or fail to exist) in the server, The server may be also referred to as the first server herein.

Any number, none, or all of the packets referenced herein may be unreliable packet(s). The packet(s) may be a unreliable datagram packet(s) (UDP). Any number, none, or all of the packets referenced herein may be a reliable packet. Any number, none, or all of the packets referenced herein may be a transmission control protocol packet (TCP). Any number, none, or all of the packets referenced herein may use reliable transport. In some embodiments, the reliable transport is TCP. In some embodiments, the reliable transport comprises a transmission control protocol packet (TCP). Reliable transport may be with at least one of XML, HTTP, and SOAP riding on top of it.

Aspects of the systems and methods described herein may be implemented as functionality programmed into any of a variety of circuitry, including programmable logic devices (PLDs), such as field programmable gate arrays (FPGAs), programmable array logic (PAL) devices, electrically programmable logic and memory devices and standard cell-based devices, as well as application specific integrated circuits (ASICs). Some other possibilities for implementing aspects of the systems and methods include: microcontrollers with memory, embedded microprocessors, firmware, software, etc. Furthermore, aspects of the systems and methods may be embodied in microprocessors having software-based circuit emulation, discrete logic (sequential and combinatorial), custom devices, fuzzy (neural network) logic, quantum devices, and hybrids of any of the above device types. Of course the underlying device technologies may be provided in a variety of component types, e.g., metal-oxide semiconductor field-effect transistor (MOSFET) technologies like complementary metal-oxide semiconductor (CMOS), bipolar technologies like emitter-coupled logic (ECL), polymer technologies (e.g., silicon-conjugated polymer and metal-conjugated polymer-metal structures), mixed analog and digital, etc.

It should be noted that the various functions or processes disclosed herein may be described as data and/or instructions embodied in various computer-readable media, in terms of their behavioral, register transfer, logic component, transistor, layout geometries, and/or other characteristics. Computer-readable media in which such formatted data and/or instructions may be embodied include, but are not limited to, non-volatile storage media in various forms (e.g., optical, magnetic or semiconductor storage media) and carrier waves that may be used to transfer such formatted data and/or instructions through wireless, optical, or wired signaling media or any combination thereof. Examples of transfers of such formatted data and/or instructions by carrier waves include, but are not limited to, transfers (uploads, downloads, email, etc.) over the Internet and/or other computer networks via one or more data transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When received within a computer system via one or more computer-readable media, such data and/or instruction-based expressions of components and/or processes under the systems and methods may be processed by a processing entity (e.g., one or more processors) within the computer system in conjunction with execution of one or more other computer programs.

Unless the context clearly requires otherwise, throughout the description and the claims, the words ‘comprise,’ ‘comprising,’ and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in a sense of ‘including, but not limited to.’ Words using the singular or plural number also include the plural or singular number respectively. Additionally, the words ‘herein,’ ‘hereunder,’ ‘above,’ ‘below,’ and words of similar import refer to this application as a whole and not to any particular portions of this application. When the word ‘or’ is used in reference to a list of two or more items, that word covers all of the following interpretations of the word: any of the items in the list, all of the items in the list and any combination of the items in the list.

The above description of illustrated embodiments of the systems and methods is not intended to be exhaustive or to limit the systems and methods to the precise form disclosed. While specific embodiments of, and examples for, the systems and methods are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the systems and methods, as those skilled in the relevant art will recognize. The teachings of the systems and methods provided herein can be applied to other processing systems and methods, not only for the systems and methods described above.

The elements and acts of the various embodiments described above can be combined to provide further embodiments. These and other changes can be made to the systems and methods in light of the above detailed description.

In general, the terms used should not be construed to limit the systems and methods to the specific embodiments disclosed in the specification and the claims, but should be construed to include all processing systems that operate under the claims. Accordingly, the systems and methods are not limited by the disclosure.

While certain aspects of the systems and methods may be presented in certain claim forms, the inventors contemplate the various aspects of the systems and methods in any number of claim forms. Accordingly, the inventors reserve the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the systems and methods. 

1. A method comprising: sending, by a first device to a second device via a connectionless protocol, a request to determine availability of data associated with the first device, wherein the second device is located remotely to the first device; receiving, from the second device via the connectionless protocol, an indication that available data is available for the first device; sending, via a reliable protocol, a request for the available data; and receiving, via the reliable protocol, the available data.
 2. The method of claim 1, wherein the sending the request for the available data comprises sending the request for the available data to a third device located remotely to the first device.
 3. The method of claim 1, wherein the sending the request for the available data comprises sending the request for the available data to the second device.
 4. The method of claim 1, wherein the connectionless protocol comprises User Datagram Protocol (UDP).
 5. The method of claim 1, wherein the connectionless protocol comprises an unreliable protocol.
 6. The method of claim 1, wherein the reliable protocol comprises Transmission Control Protocol (TCP).
 7. The method of claim 1, wherein the reliable protocol comprises at least one of an acknowledgement-based protocol or a connection-based protocol.
 8. The method of claim 1, wherein the receiving the available data comprises receiving the available data from a third device located remotely to the first device.
 9. The method of claim 1, wherein the sending the request for the available data comprises sending the request for the available data via the reliable protocol and using at least one of Extensible Markup Language (XML), HyperText Transfer Protocol (HTTP), or Simple Object Access Protocol (SOAP).
 10. A first device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the first device to: send, to a second device via a connectionless protocol, a request to determine availability of data associated with the first device, wherein the second device is located remotely to the first device; receive, from the second device via the connectionless protocol, an indication that available data is available for the first device; send, via a reliable protocol, a request for the available data; and receive, via the reliable protocol, the available data.
 11. The first device of claim 10, wherein the connectionless protocol comprises User Datagram Protocol (UDP).
 12. The first device of claim 10, wherein the connectionless protocol comprises an unreliable protocol.
 13. The first device of claim 10, wherein the reliable protocol comprises Transmission Control Protocol (TCP).
 14. The first device of claim 10, wherein the reliable protocol comprises at least one of an acknowledgement-based protocol or a connection-based protocol.
 15. The first device of claim 10, wherein the instructions that, when executed, cause the first device to send the request for the available data comprise instructions that cause the first device to send the request for the available data to a third device located remotely to the first device.
 16. A non-transitory computer-readable medium storing instructions that, when executed, cause: sending, by a first device to a second device via an connectionless protocol, a request to determine availability of data associated with the first device, wherein the second device is located remotely to the first device; receiving, from the second device via the connectionless protocol, an indication that available data is available for the first device; sending, via a reliable protocol, a request for the available data; and receiving, via the reliable protocol, the available data.
 17. The non-transitory computer-readable medium of claim 16, wherein the connectionless protocol comprises User Datagram Protocol (UDP); and wherein the reliable protocol comprises Transmission Control Protocol (TCP).
 18. The non-transitory computer-readable medium of claim 16, wherein the connectionless protocol comprises an unreliable protocol.
 19. The non-transitory computer-readable medium of claim 16, wherein the reliable protocol comprises at least one of an acknowledgement-based protocol or a connection-based protocol.
 20. The non-transitory computer-readable medium of claim 16, wherein the reliable protocol is used in combination with at least one of Extensible Markup Language (XML), HyperText Transfer Protocol (HTTP), or Simple Object Access Protocol (SOAP). 